FHIR © HL7.org  |  Server Home  |  FHIR Server FHIR Server 3.4.11  |  FHIR Version n/a  User: [n/a]

Resource ValueSet/FHIR Server from package hl7.terminology#current (32 ms)

Package hl7.terminology
Type ValueSet
Id Id
FHIR Version R5
Source http://terminology.hl7.org/https://build.fhir.org/ig/HL7/UTG/ValueSet-v3-xActMoodOrdPrmsEvn.html
Url http://terminology.hl7.org/ValueSet/v3-xActMoodOrdPrmsEvn
Version 3.0.0
Status active
Date 2014-03-26
Name XActMoodOrdPrmsEvn
Title x_ActMoodOrdPrmsEvn
Experimental False
Realm uv
Authority hl7
Description A grouping of Order, Promise and Event moods.
Copyright This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html

Resources that use this resource

No resources found


Resources that this resource uses

CodeSystem
v3-ActMood ActMood


Narrative

Note: links and images are rebased to the (stated) source

Generated Narrative: ValueSet v3-xActMoodOrdPrmsEvn

Language: en

  • Include these codes as defined in http://terminology.hl7.org/CodeSystem/v3-ActMood
    CodeDisplayDefinition
    EVNevent (occurrence)**Definition:** An act that actually happens (may be an ongoing act or a documentation of a past act).
    PRMSpromise**Definition:** A commitment to perform an act (may be either solicited or unsolicited). The committer becomes responsible to the other party for executing the act, and, as a consequence, the other party may rely on the first party to perform or cause to perform the act.

    **UsageNotes:** Commitments may be retracted or cancelled.
    RQOrequest**Definition:** A request act that is specialized for an event request/fulfillment cycle.

    **UsageNotes:** The fulfillment cycle may involve intermediary fulfilling acts in moods such as PRMS, APT, or even another RQO before being fulfilled by the final event.

    **UsageNotes:** The concepts of a "request" and an "order" are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. "Orders" are commonly refused for a variety of clinical and business reasons, and the notion of a "request" obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is "request."

    Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the "local" business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept.

    The critical distinction here, is the difference between this concept and an "intent", of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.

Source

{
  "resourceType" : "ValueSet",
  "id" : "v3-xActMoodOrdPrmsEvn",
  "language" : "en",
  "text" : {
    "status" : "extensions",
    "div" : "<div xmlns=\"http://www.w3.org/1999/xhtml\" xml:lang=\"en\" lang=\"en\"><p class=\"res-header-id\"><b>Generated Narrative: ValueSet v3-xActMoodOrdPrmsEvn</b></p><a name=\"v3-xActMoodOrdPrmsEvn\"> </a><a name=\"hcv3-xActMoodOrdPrmsEvn\"> </a><a name=\"v3-xActMoodOrdPrmsEvn-en-US\"> </a><div style=\"display: inline-block; background-color: #d9e0e7; padding: 6px; margin: 4px; border: 1px solid #8da1b4; border-radius: 5px; line-height: 60%\"><p style=\"margin-bottom: 0px\">Language: en</p></div><ul><li>Include these codes as defined in <a href=\"CodeSystem-v3-ActMood.html\"><code>http://terminology.hl7.org/CodeSystem/v3-ActMood</code></a><table class=\"none\"><tr><td style=\"white-space:nowrap\"><b>Code</b></td><td><b>Display</b></td><td><b>Definition</b></td></tr><tr><td><a href=\"CodeSystem-v3-ActMood.html#v3-ActMood-EVN\">EVN</a></td><td style=\"color: #cccccc\">event (occurrence)</td><td>**Definition:** An act that actually happens (may be an ongoing act or a documentation of a past act).</td></tr><tr><td><a href=\"CodeSystem-v3-ActMood.html#v3-ActMood-PRMS\">PRMS</a></td><td style=\"color: #cccccc\">promise</td><td>**Definition:** A commitment to perform an act (may be either solicited or unsolicited). The committer becomes responsible to the other party for executing the act, and, as a consequence, the other party may rely on the first party to perform or cause to perform the act.<br/><br/>**UsageNotes:** Commitments may be retracted or cancelled.</td></tr><tr><td><a href=\"CodeSystem-v3-ActMood.html#v3-ActMood-RQO\">RQO</a></td><td style=\"color: #cccccc\">request</td><td>**Definition:** A request act that is specialized for an event request/fulfillment cycle.<br/><br/>**UsageNotes:** The fulfillment cycle may involve intermediary fulfilling acts in moods such as PRMS, APT, or even another RQO before being fulfilled by the final event.<br/><br/>**UsageNotes:** The concepts of a &quot;request&quot; and an &quot;order&quot; are viewed as different, because there is an implication of a mandate associated with order. In practice, however, this distinction has no general functional value in the inter-operation of health care computing. &quot;Orders&quot; are commonly refused for a variety of clinical and business reasons, and the notion of a &quot;request&quot; obligates the recipient (the fulfiller) to respond to the sender (the author). Indeed, in many regions, including Australia and Europe, the common term used is &quot;request.&quot;<br/><br/>Thus, the concept embodies both notions, as there is no useful distinction to be made. If a mandate is to be associated with a request, this will be embodied in the &quot;local&quot; business rules applied to the transactions. Should HL7 desire to provide a distinction between these in the future, the individual concepts could be added as specializations of this concept.<br/><br/>The critical distinction here, is the difference between this concept and an &quot;intent&quot;, of which it is a specialization. An intent involves decisions by a single party, the author. A request, however, involves decisions by two parties, the author and the fulfiller, with an obligation on the part of the fulfiller to respond to the request indicating that the fulfiller will indeed fulfill the request.</td></tr></table></li></ul></div>"
  },
  "extension" : [
    {
      "extension" : [
        {
          "url" : "name",
          "valueString" : "Name:Class"
        },
        {
          "url" : "value",
          "valueString" : "ProcessPromise"
        }
      ],
      "url" : "http://terminology.hl7.org/StructureDefinition/ext-mif-assocConceptProp"
    }
  ],
  "url" : "http://terminology.hl7.org/ValueSet/v3-xActMoodOrdPrmsEvn",
  "identifier" : [
    {
      "system" : "urn:ietf:rfc:3986",
      "value" : "urn:oid:2.16.840.1.113883.1.11.16730"
    }
  ],
  "version" : "3.0.0",
  "name" : "XActMoodOrdPrmsEvn",
  "title" : "x_ActMoodOrdPrmsEvn",
  "status" : "active",
  "experimental" : false,
  "date" : "2014-03-26",
  "publisher" : "Health Level Seven International",
  "contact" : [
    {
      "telecom" : [
        {
          "system" : "url",
          "value" : "http://hl7.org"
        },
        {
          "system" : "email",
          "value" : "hq@HL7.org"
        }
      ]
    }
  ],
  "description" : "A grouping of Order, Promise and Event moods.",
  "immutable" : true,
  "copyright" : "This material derives from the HL7 Terminology THO. THO is copyright ©1989+ Health Level Seven International and is made available under the CC0 designation. For more licensing information see: https://terminology.hl7.org/license.html",
  "compose" : {
    "include" : [
      {
        "system" : "http://terminology.hl7.org/CodeSystem/v3-ActMood",
        "concept" : [
          {
            "code" : "EVN"
          },
          {
            "code" : "PRMS"
          },
          {
            "code" : "RQO"
          }
        ]
      }
    ]
  }
}

XIG built as of ??metadata-date??. Found ??metadata-resources?? resources in ??metadata-packages?? packages.